Experimental control in software reliability certification

There is growing interest in software 'certification', i.e., confirmation that software has performed satisfactorily under a defined certification protocol. Regulatory agencies, customers, and prospective reusers all want assurance that a defined product standard has been met. In other industries, products are typically certified under protocols in which random samples of the product are drawn, tests characteristic of operational use are applied, analytical or statistical inferences are made, and products meeting a standard are 'certified' as fit for use. A warranty statement is often issued upon satisfactory completion of a certification protocol. This paper outlines specific engineering practices that must be used to preserve the validity of the statistical certification testing protocol. The assumptions associated with a statistical experiment are given, and their implications for statistical testing of software are described

Cleanroom Software Engineering - Reference Model Version 1.0

ion techniques---for example, conditions on stimulus histories---permit compact descriptions in scaling up to large systems. A state box is derived from and verified against a corresponding black box. The state box transition function is ((current stimulus, current state) --> (response, new state)). That is, a state box maps the current stimulus and the current state into a response and a new state. In the state box, the stimulus history of the black box is replaced by retained state data necessary to achieve black box behavior. A state box definition is procedure-free, and isolates and focuses on state invention. State box definitions are often given in tables with columns for current stimulus, current state, response, and new state. A clear box is derived from and verified against a corresponding state box. The clear box transition function is ((current stimulus, current state) --> (response, new state)) by procedures. In the clear box, the procedures required to implement the state ..

Cleanroom Software Engineering Reference

Cleanroom software engineering is a theory-based team-oriented process for development and certification of high-reliability software systems under statistical quality control. A principal objective of the Cleanroom process is development of software that exhibits zero failures in use. The Cleanroom name is borrowed from hardware Cleanrooms, with their emphasis on rigorous engineering discipline and focus on defect prevention rather than defect removal. Cleanroom combines mathematically based methods of software specification, design, and correctness verification with statistical, usage-based testing to certify software fitness for use. Cleanroom projects have reported substantial gains in quality and productivity. This report defines the Cleanroom Software Engineering Reference Model, or CRM. The CRM is expressed in terms of a set of 14 Cleanroom processes and 20 work products. It is intended as a guide for Cleanroom project management and performance, process assessment and improvement, and technology transfer and adoption

Cleanroom Software Engineering Implementation of the Capability Maturity Model (CMMsm) for Software

The Capability Maturity Model for Software (CMM) developed by the Software Engineering Institute, and Cleanroom Software Engineering developed by Dr. Harlan Mills and his associates in IBM and other organizations, share a common concern with software quality and the effectiveness of software development. The principal focus of the CMM is on process management maturity; the principal focus of Cleanroom is on rigorous engineering processes. The CMM management processes and the Cleanroom engineering processes are complementary and mutually reinforcing. The Capability Maturity Model for Software describes the principles and practices underlying software process maturity. It is intended to help software organizations improve the maturity of their software processes through an evolutionary path from ad hoc, chaotic processes to mature, disciplined software processes. The CMM is organized into five maturity levels. The maturity levels are defined in terms of 18 key process areas (KPAs) that characterize project performance at each level. Cleanroom software engineering is a theory-based engineering process for development and certification of high-reliability software systems under statistical quality control. Cleanroom is intended to help software organizations improve their ability to apply engineering discipline to software development. Cleanroom is defined in terms of 14 processes that implement the technology and operations involved in Cleanroom software development